OK, so in this particular lecture, I'm going to talk about the reasons why we should consider doing
using knew of him or why use the competitor to them now, you wouldn't think that this would actually
be a controversial subject, but it actually is.
You wouldn't think that using a particular type of text editor would result in heated debates, but
it actually does.
So I'm going to kind of skip the controversy a bit and kind of just give you the basic rationale of
why many people, former View's former users and current users are actually switching to Vem Neerim.
And when I outline the reasons, you'll understand it.
Nuveen is a vem alternative that is based mostly upon them architecture, you can do pretty much everything
with new vim as you can with them, but there are some significant improvements and that's where we
really want to concentrate on is the significant improvement.
Now, neither of them helps solve very important problems that currently exist with them, since Vim
was actually designed and built, I think, in the very advent of Linux 20, 30, 40 years ago.
It is a synchronous program.
It doesn't use asynchronous loading of plug ins, which means plug in fails and lock up the whole program
as well.
Since the plug ins are asynchronous, they load faster, which is the whole point of using a text editor
such as VM to help you get your job done quicker.
There has been an increase in improving them since the advent of Novem, and that just helps out everything.
So really more people contributing to both projects, it means that features are added to many of them
and also to them.
So it's kind of counterintuitive, but by supporting many of them were actually also supporting them,
the main product or the main Ed.
But there is a caveat, and that is that Nerem is still in beta and as such can be unstable.
The stability is improving at each iteration.
So with each update, it gets more and more stable.
But you should be aware of this.
So I wouldn't focus a large focus on anything, a large project with necessarily.
And because he could put your project at risk, but if you see him often and back up your source code
to an external source such as GitHub or an external get server you may control, it kind of negates
the problem.
At least you'll be able have some point of failure.
If you want to use Novem and it's based largely upon them and you already know them, the learning curve
is significantly shortened.
Setting up in migrating to new isn't that much work, but there are some nuances you might want to be
aware of beforehand.
So using new them actually supports them.
It supports supports both you want to create also a competition in the marketplace, even in an open
source code environment, so that you have people trying to basically add features from Novem to them
and basically helping them become more stable.
Now, using new vim and vim can create one of the more powerful ways to edit and write code.
I strongly recommend using both because as well as any key findings in any tech center such as Visual
Studio Code, and once you start down this path of using them, you see how much more you can get done
in the day, which is kind of the point of using them in vim key bindings and vim, you know, the whole
the whole.
When you get into the whole universe of using them, then your efficiency can be improved.
Obviously there is more to it than just typing.
You want to actually, you know, be able to think better and, you know, understand your code better
so that you can, you know, get things more things done in the day.
But if you don't have to be slowed down by your mouse and you can just use key bindings and just quickly,
right through code, all the better.